Transporting object packets in a nested system landscape

ABSTRACT

Described are methods and systems related to transporting one or more object packets present in a nested hierarchy of one or more system landscapes. The object packets available for transporting from source systems to target systems present in the nested hierarchy of the system landscapes is identified. A transport request is generate for a collection of object packets of each source system in the nested hierarchy of the system landscapes. The transport requests are aggregated to render a nested transport collection. The nested transport collection is transported within the nested hierarchy of the system landscapes. The nested transport collection is deployed to assign the transport requests present in the nested transport collection to the target systems present in the nested hierarchy of the system landscapes.

TECHNICAL FIELD

Embodiments of the invention generally relate to computer systems, andmore particularly to methods and systems for transporting objectpackets.

BACKGROUND

Software systems are usually not standalone; rather they are a part of anetwork of systems also called system landscapes. Various factorscontribute to the complexity of these system landscapes. For instance,different applications that are running on different systems may beinterconnected to each other by business processes, constitutingvertical complexity. Applications that are installed more than once in asystem, run independent of processes being executed in the system. Anynew result of such processes may have to be transported across allapplications, constituting horizontal complexity. When the output datais proprietary, coming from various servers, the format may not beuniform, constituting server complexity. To make these complex systemlandscapes controllable, a hierarchical landscaping of systems isrequired. However, in an already existing organizational hierarchy, thehierarchical landscaping of systems may incur other complexitiesincluding multi-level vertical and horizontal complexities. Thehierarchy may also include heterogeneous system landscapes, withheterogeneous systems. The output data of each of the heterogeneoussystems are unique in nature. The hierarchy does not supporttransportation of such unique output data to other system.

Hence, there is a need for a method to transport information in ahierarchical environment, thereby avoiding complexities incurred duringtransportation.

SUMMARY

Embodiments of the invention are generally directed to methods andsystem for transporting one or more object packets present in a nestedhierarchy of one or more system landscapes. The object packets availablefor transporting from source systems to target systems present in thenested hierarchy of the system landscapes is identified. A transportrequest is generated for a collection of object packets of each sourcesystem in the nested hierarchy. The transport requests are aggregated torender nested transport collections. The nested transport collectionsare transported within the nested hierarchy. The nested transportcollections are further deployed to assign the transport requestspresent in the nested transport collections to the target systemspresent in the nested hierarchy of the system landscapes.

In an embodiment, the object packets available for transporting from thesource systems to the target systems at a first level of the nestedhierarchy are identified. A first level transport request is generatedfor a collection of object packets of each source system present in thefirst level of the nested hierarchy. The first level transport requestsgenerated for the source systems at the first level of the nestedhierarchy are aggregated to render a second level transport collectionat a second level of the nested hierarchy. The second level transportcollections rendered at the second level of the nested hierarchy areaggregated to generate a third level transport collection at a thirdlevel of the nested hierarchy. Similarly, n^(th) level transportcollections rendered at an n^(th) level of the nested hierarchy areaggregated to generate an n+1 level transport collection at an n+1 levelof the nested hierarchy.

Further, the n+1 level transport collection is transported within then+1 level of the nested hierarchy. The n+1 transport collection isdeployed at the n^(th) level of the nested hierarchy to assign then^(th) level transport collections present in the n+1 transportcollection to corresponding hierarchies present at the n^(th) level ofthe nested hierarchy. Similarly, the third level transport collection isdeployed at the second level of the nested hierarchy, to assign thesecond level transport collections present in the third level transportcollection to the second level of the nested hierarchy. The second leveltransport collections are deployed at the first level of the nestedhierarchy to assign the first level transport requests present in thesecond level transport collection to the target systems in the firstlevel of the nested hierarchy.

In another embodiment, at the n+1 level of the nested hierarchy, if oneor more n+1 level transport collections are already present, the n+2level transport collection may be aggregated with the n+1 leveltransport collection to generate an aggregated n+2 level transportcollection. Further the n+1 level transport collections aggregated withan n+2 level transport collection are deployed at the n+1 level of thenested hierarchy.

These and other benefits and features of embodiments of the inventionwill be apparent upon consideration of the following detaileddescription of preferred embodiments thereof, presented in connectionwith the following drawings in which like reference numerals are used toidentify like elements throughout.

BRIEF DESCRIPTION OF THE DRAWINGS

The claims set forth the embodiments of the invention withparticularity. The invention is illustrated by way of example and not byway of limitation in the figures of the accompanying drawings in whichlike references indicate similar elements. The embodiments of theinvention, together with its advantages, may be best understood from thefollowing detailed description taken in conjunction with theaccompanying drawings.

FIG. 1 is a block diagram providing a conceptual illustration of anoverall method of transporting one or more object packets present in anested hierarchy of one or more system landscapes, according to anembodiment of the invention.

FIG. 2A is a block diagram illustrating an exemplary process fortransporting one or more object packets present in a nested hierarchy ofone or more system landscapes, according to an embodiment of theinvention.

FIG. 2B is a block diagram illustrating an exemplary process fortransporting one or more object packets present in one or morehierarchies of one or more system landscapes, included in a nestedhierarchy of the system landscapes, according to an embodiment of theinvention.

FIG. 3 is a flow diagram illustrating a process diagram for transportingone or more object packets present in a nested hierarchy of one or moresystem landscapes, according to an embodiment of the invention.

FIG. 4 illustrates a block diagram of a system for transporting one ormore object packets present in a nested hierarchy of one or more systemlandscapes, according to an embodiment of the invention.

FIG. 5 illustrates a block diagram of an exemplary computer system andenvironment for implementing the principles and techniques discussedherein for transporting one or more object packets present in a nestedhierarchy of one or more system landscapes, according to an embodimentof the invention.

DETAILED DESCRIPTION

Embodiments of the invention are generally directed to methods andsystems related to transporting one or more object packets present in anested hierarchy of one or more system landscapes. A nested hierarchy ofthe system landscapes includes one or more of hierarchies of one or moresystem landscapes. A hierarchy of system landscapes includes acollection or an arrangement of one or more system landscapes. Eachsystem landscape includes one or more source systems and correspondingone or more target systems. The source systems present in the hierarchymay include a collection of homogeneous and/or heterogeneous data thatis required by the target systems present in the same hierarchy or adifferent hierarchy, to execute necessary processes. The homogeneous orheterogeneous data may be described as object packets. In an embodiment,transporting the object packets present in the nested hierarchy of thesystem landscapes involves transporting the object packets from thesource systems of a hierarchy of system landscape to the target systemsof the hierarchy of system landscape. In another embodiment,transporting the object packets present in the hierarchy of systemlandscapes involves transporting object packets from the source systemsof a first hierarchy of system landscapes to the target systems of asecond hierarchy of system landscapes. The first and the secondhierarchy of system landscapes are included in the nested hierarchy ofthe system landscapes.

The target systems that receive the object packets are present in thehierarchy of system landscapes whose structure is similar to thehierarchy of system landscapes that include the source systems thattransport the object packets. The structure of a hierarchy of systemlandscapes may be described as an arrangement of the source systems andthe target systems of the system landscapes. The object packetsavailable for transporting from the source systems in the hierarchy ofsystem landscapes to the target systems present in a nested hierarchy ofthe system landscapes are identified. A transport request is generatedfor a collection of object packets of each source system in the nestedhierarchy of the system landscapes. The transport requests areaggregated to render a transport collection. The transport collection istransported to the target systems in the nested hierarchy of the systemlandscapes. The transport collection is further deployed to assign thetransport requests present in the transport collection to one or morecorresponding target systems present in the nested hierarchy of thesystem landscapes.

In the following description, numerous specific details are set forth toprovide a thorough understanding of embodiments of the invention. Oneskilled in the relevant art will recognize, however, that the inventioncan be practiced without one or more of the specific details, or withother methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

Reference throughout this specification to “one embodiment”, “thisembodiment” and similar phrases, means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,the appearances of these phrases in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

FIG. 1 is a block diagram providing a conceptual illustration of anoverall method of transporting one or more object packets present in anested hierarchy of one or more system landscapes, according to anembodiment of the invention. A source system may be described as asystem that executes one or more processes to render an output data. Forinstance, a source system may be an analysis system that executes adevelopment process for analyzing a report and render output data as aresult. A target system may be described as a system that executes oneor more processes subsequent to the processes executed by the sourcesystem, to render a subsequent output data. In an embodiment, a sourcesystem has one or more corresponding target systems. In such cases, theoutput data of the source system may be required by the correspondingtarget system for further processing. Hence, the output data of thesource system has to be transported to the corresponding target systemfor further processing.

In an embodiment, a system landscape may include a development system, aquality assurance system, and a production system. An output of thedevelopment system may be transported to the quality assurance systemand the production system. The development system may include one ormore source systems, and the quality assurance system and productionsystem may each include one or more target systems. Many such systemlandscapes put together form a hierarchy of system landscapes. Ahierarchy of system landscapes may include system landscapes supportingvarious processes. For instance, a hierarchy of system landscapes mayinclude a business application landscape, a report creation systemlandscape, a report analyzing system landscape, a resource planningsystem landscape, and the like. The output data of each such system maybe unique, thus making the collection of the output data of all thesystems heterogeneous. A plurality of the hierarchy of system landscapesis described as a nested hierarchy of the system of landscapes.

The output data available in the source system is described as objectpacket. An object packet is a collection of output data of a sourcesystem, and output data from various applications that may be associatedwith a source system. The object packets may also include developmentresults of each source system (e.g., a development system). Adevelopment result may be described as a collection of data that isresulting for a development process executed on the source system. Theoutput data of the source system may be in a particular file formatdepending upon a type of output data. For instance, the output data ofreport analyzing system may have a particular file format. Files mayrepresent a collection of output data of a same format, for instance,application component files, service component files and the like. Thusthe object packet represents a file format of the type of output dataincluded in it. For instance, if the output data is of a document type(e.g., Microsoft® Word), the file format of the output data may be ofthe type “.doc”. Thus, the object packet representing such a file formatmay also be of the type “.doc”.

Transporting object packets from a source system to a target systemincludes transporting object packets from a source system where theobject packets represent the output of a process executed by the sourcesystem. For instance, a process integration (PI) system landscape mayinclude a process integration development system, a process integrationquality assurance system and a process integration production system.The output data of PI development system is transported to the PIquality assurance system and further to the PI production system. Ahierarchical system may include many such homogeneous and/orheterogeneous system landscapes. Block diagram 100 illustrates theoverall method involved in transporting object packets from the sourcesystem (e.g., development system) of each of such system landscapes tothe target system (e.g., quality testing system and/or productionsystem).

The object packets may be transported from one or more source systemspresent in a hierarchy of system landscapes to one or more correspondingtarget systems present in the same hierarchy of system landscapes. In anembodiment, transporting object packets present in the hierarchy ofsystem landscapes involves transporting object packets from sourcesystems of a first hierarchy of system landscapes to correspondingtarget systems of a second hierarchy of system landscapes. The first andthe second hierarchy of system landscapes are included in the nestedhierarchy of the system landscapes. The target systems that receive theobject packets are present in the hierarchy of system landscapes whosestructure is similar to the hierarchy of system landscapes that includethe source systems that transport the object packets.

Source systems and target systems of the system landscapes may beincluded in source block 105 and target block 145 respectively. Ahierarchy of system landscapes includes one or more of such sourceblocks and target blocks. A nested hierarchy of the system landscapesincludes one or more of such hierarchies. Source block 105 includes agroup of one or more source systems, “source system 1” 110, “sourcesystem 2” 115, “source system n” 120, and the like. Each of the sourcesystems (e.g., 110, 115, and 120) is operable to execute a specificprocess to render an output data for the process. The output data isrepresented by object packets. Target block 145 includes a group of oneor more target systems corresponding to the source systems in sourceblock 105, including “target system 1” 150, “target system 2” 155,“target system 3” 160 and the like. Each of the target systems (e.g.,150, 155, and 160) is operable to execute a process subsequent to theprocess executed at the corresponding source system, and render asubsequent output data for the subsequent process. Transportationcontroller 125 is configured to facilitate transporting the objectpackets from source block 105 to target block 145.

To transport the output data from the source systems present in sourceblock 105 to the target systems present in target block 145,transportation controller 125 identifies the object packets that areavailable for transporting from each source system (e.g., 110, 115, and120) to the target system (e.g., 150, 155, and 160). Transportationcontroller 125 identifies a collection of one or more object packetsavailable at each source system. At 130, transportation controller 125generates a transport request for each collection of object packetsavailable at each source system present in source block 105 of thehierarchy of system landscapes. A transport request represents acollection of object packets available at a source system, fortransporting to the target systems. For instance, for the collection ofobject packets available at source system 110, a first transport requestis generated by transportation controller 125. Similarly, for thecollection of object packets available at source system 115, a secondtransport request is generated and for the collection of object packetsavailable at source system 120, an n^(th) transport request is generatedby transportation controller 125. Each transport request represents aformat of a type of output data present in the object packets includedin the transport request. For instance, if the object packet representsa file format of a type “.doc”, the transport request including such anobject packet also represents a file format of a type “.doc”. In anembodiment, the collection of output data present in the object packetmay be grouped to create the transport request. In another embodiment,the transport request is persisted as a file.

At 135, transportation controller 125 aggregates the transport requestsavailable at each source system (e.g., 110, 115 and 120). Aggregatingthe transport requests includes collecting the transport requests foreach source system. For instance, the first transport request, thesecond transport request and the n^(th) transport request generated atsource systems 110, 115 and 120 respectively are aggregated bytransportation controller 125, to create a nested transport collection.The nested transport collection represents one or more transportcollections rendered at one or more different levels of the nestedhierarchy. The nested transport collection is rendered in a hierarchyidentical to the nested hierarchy of the system landscapes. In otherwords, the nesting of the nested transport collection is similar to thenesting of the hierarchies of the system landscape. The transportcollection represents a collection of transport requests available atall the source systems present in source block 105. For instance,transport collection for system block 105 includes an aggregation of thefirst transport request generated for source system 110, the secondtransport request generated for source system 115, and the n^(th)transport request generated for source system 120. The transportcollection represents a format of a type of object packets present inthe transport requests included in the transport collection.

The nested transport collection is transported within the nestedhierarchy. For instance, at 140, transportation controller 125transports the transport collection rendered for the source systems insource block 105 to the corresponding target systems in target block145. In an embodiment, transportation controller 125 includes an indexthat stores a transport directory including an identity of the sourcesystems and the corresponding target systems. For instance, for sourcesystem 110, the transport directory includes an identity of sourcesystem 110, with an address “AAAS1”, identity of source system 115, withan address “AAAS2”, and identity of source system 120, with an address“AAASn”. Similarly for target system 150, the transport directoryincludes an identity of target system 150, with an address “AAAT1”,identity of source system 155, with an address “AAAT2”, and identity oftarget system 160, with an address “AAATn”. The index recognizes acorresponding target system that is associated with a source system bymapping the addresses of the source system and the target system. Theidentity facilitates in identifying a corresponding target system forevery source system. Based upon the transport directory, transportationcontroller 125 transports the transport collection to correspondingtarget systems. In an embodiment, the transport collection is persisted.

Transportation controller 125 is operable for deploying the nestedtransport collection to assign the transport requests present in thenested transport collection to target block 145. Deploying the nestedtransport collection may include importing transport collections presentin the nested transport collection, extracting the transport requestspresent in each transport collection, identifying the source systemsassociated with each transport request, identifying the object packetsavailable in each transport request, and assigning the object packets ofeach source system to a corresponding target system. Transportationcontroller 125 aggregates the transport collections from all thehierarchies of system landscapes present in the nested hierarchy of thesystem landscapes and transport the aggregated transport collections toone or more corresponding hierarchies of system landscapes.

The transport collection may be transported to multiple hierarchies ofsystem landscapes, having multiple levels of nested hierarchy, byrecursively aggregating the transport collections at each level ofnested hierarchy. In an embodiment, the object packets available fortransporting from the source systems to the target systems at a firstlevel of the nested hierarchy are identified. A first level transportrequest is generated for a collection of object packets of each sourcesystem present in the first level of the nested hierarchy. The firstlevel transport requests generated for the source systems at the firstlevel of the nested hierarchy are aggregated to render a second leveltransport collection at a second level of the nested hierarchy. Thesecond level transport collections rendered at the second level of thenested hierarchy are aggregated to generate a third level transportcollection at a third level of the nested hierarchy. Similarly, n^(th)level transport collections rendered at an n^(th) level of the nestedhierarchy are aggregated to generate an n+1 level transport collectionat an n+1 level of the nested hierarchy.

Further, the n+1 level transport collection is transported within then+1 level of the nested hierarchy. The n+1 transport collection isdeployed at the n^(th) level of the nested hierarchy to assign then^(th) level transport collections present in the n+1 transportcollection to corresponding hierarchies present the n^(th) level of thenested hierarchy. Similarly, the third level transport collection isdeployed at the third level of the nested hierarchy, to assign thesecond level transport collections to the second level of the nestedhierarchy. The second level transport collections are deployed at thesecond level of the nested hierarchy to assign the first level transportrequests to the target systems in the first level of the nestedhierarchy.

In an embodiment, a transport collection rendered for any source blockpresent in the hierarchy of system landscapes can be transported to oneor more corresponding target blocks present in the same hierarchy ofsystem landscapes, or to one or more target blocks present in anotherhierarchy of system landscape of the nested hierarchy of the systemlandscapes.

FIG. 2A is a block diagram illustrating an exemplary process fortransporting one or more object packets present in a nested hierarchy ofone or more system landscapes, according to an embodiment of theinvention. FIG. 2A illustrates a two-level nested hierarchy fortransporting object packets present in a hierarchy of system landscapes.A first level 227 includes one hierarchy of system landscapes, for e.g.hierarchy of system landscapes 200. Hierarchy of system landscapes 200includes system landscapes 201, 203 and 205. Each of the systemlandscapes include source systems and target systems. For instance,system landscapes 201, 203 and 205 include “source system 1” 204,“source system 2” 208, and “source system 3” 212 as source systems and“target system 1” 222, “target system 2” 224, and “target system 3” 226as target systems. The source systems may be contained in source block202 and the target systems may be contained in target block 220.Transportation controller 218 is operable for transporting objectpackets from source block 202 to target block 220. Transportationcontroller 218 identifies the object packets available for transportingfrom each of the source systems 204, 208 and 212, to the correspondingtarget systems 222, 224 and 226 respectively. Transportation controller218 generates first level transport requests 206, 210 and 214respectively for each of the source systems 204, 208 and 212.

At second level 228, transportation controller 218 aggregates firstlevel transport requests 206, 210 and 214 to render second leveltransport collection 216. Transportation controller 218 transportssecond level transport collection 216 to target block 220, to deploysecond level transport collection 216 at respective target systems (fore.g. 222, 224, and 226).

FIG. 2B illustrates an exemplary process for transporting one or moreobject packets present in one or more hierarchies of one or more systemlandscapes, present in a nested hierarchy of the system landscapes,according to an embodiment of the invention. FIG. 2B illustrates athree-level nested hierarchy for transporting object packets present inmultiple hierarchies of system landscapes. At a first level, the objectpackets available for transporting from the source systems to the targetsystems are identified. A first level transport request is generated fora collection of object packets of each source system present in thefirst level of the nested hierarchy. The first level transport requestis generated in a hierarchy that is identical to the nested hierarchy ofthe system landscapes. The first level transport requests generated forall the source systems at the first level of the nested hierarchy areaggregated to render a second level transport collection at a secondlevel of the nested hierarchy. One or more such second level transportcollections rendered at the second level of the nested hierarchy areaggregated to generate third level transport collection at a third levelof the nested hierarchy.

The third level transport collection is transported to the second levelof the nested hierarchy. The third level transport collection isdeployed at the second level of the nested hierarchy, to assign thesecond level transport collections present in the third level transportcollection to the corresponding hierarchies present in the nestedhierarchy of system landscapes. Further, the second level transportcollections are deployed at the first level of the nested hierarchy toassign the first level transport requests present in each second leveltransport collection to the target systems present in the first level ofthe hierarchy.

First level 238 includes three hierarchies of system landscapes, fore.g. hierarchy of system landscapes 200A, hierarchy of system landscapes200B and hierarchy of system landscapes 200C. Nested hierarchy of thesystem landscapes 244 includes hierarchies of system landscapes 200A,200B and 200C.

Hierarchy of system landscapes 200A includes system landscapes 201A,203A and 205A. Each of the system landscapes include source systems andtarget systems. For instance, system landscapes 201A, 203A and 205Ainclude “source system 1” 204A, “source system 2” 208A, and “sourcesystem 3” 212A as source systems and “target system 1” 222A, “targetsystem 2” 224A, and “target system 3” 226A as target systems. The sourcesystems may be contained in source block 202A and the target systems maybe contained in target block 220A. Similarly hierarchy of systemlandscapes 200B includes system landscapes 201B, 203B and 205B. Each ofthe system landscapes include source systems and target systems. Forinstance, system landscapes 201B, 203B and 205B include “source system1” 204B, “source system 2” 208B, and “source system 3” 212B as sourcesystems and “target system 1” 222B, “target system 2” 224B, and “targetsystem 3” 226B as target systems. The source systems may be contained insource block 202B and the target systems may be contained in targetblock 220B. Hierarchy of system landscapes 200C includes systemlandscapes 201C, 203C and 205C. Each of the system landscapes includesource systems and target systems. For instance, system landscapes 201C,203C and 205C include “source system 1” 204C, “source system 2” 208C,and “source system 3” 212C as source systems and “target system 1” 222C,“target system 2” 224C, and “target system 3” 226C as target systems.The source systems may be contained in source block 202C and the targetsystems may be contained in target block 220C.

A transportation controller is operable for transporting object packetsfrom the source blocks to the target blocks. These target blocks may betarget blocks of the same hierarchy, target blocks of a differenthierarchy or even source blocks of a different hierarchy that areoperable to accept object packets from other source blocks. In anembodiment, the source blocks of a hierarchy that are operable to acceptthe object packets may utilize the object packets that are transportedfrom the source blocks of another hierarchy to output object packetsthat is be further transported to target blocks in the nested hierarchy.

At second level 240, second level transportation controller 218A isoperable for transporting object packets from source block 202A to thetarget systems present in nested hierarchy of the system landscapes 244.For instance, second level transportation controller 218A transports theobject packets from source block 202A to target block 220A present inhierarchy of landscapes 200A. Second level transportation controller218A may also be operable for transporting object packets from sourceblock 202A to third level transport controller 230. Similarly, secondlevel transportation controller 218B is operable for transporting objectpackets from source block 202B to the target systems present in nestedhierarchy of the system landscapes 244. Second level transportationcontroller 218C is operable for transporting object packets from sourceblock 202C to the target systems present in nested hierarchy of thesystem landscapes 244.

At first level 238, second level transportation controller 218Aidentifies the object packets available for transporting from each ofthe source systems 204A, 208A and 212A, to the target systems present innested hierarchy of the system landscapes 244. Second leveltransportation controller 218A generates first level transport requests206A, 210A and 214A respectively for each of the source systems 204A,208A and 212A. Second level transportation controllers 218B and 218Cperform the same steps for the respective source systems.

At second level 240, second level transportation controller 218Aaggregates first level transport requests 206A, 210A and 214A to rendersecond level transport collection 216A. Similarly, second leveltransportation controller 218B aggregates transport requests 206B, 210Band 214B to render second level transport collection 216B and secondlevel transportation controller 218C aggregates first level transportrequests 206C, 210C and 214C to render second level transport collection216C. In an embodiment, second level transport controller 218A, 218B and218C transport second level transport collections 216A, 216B and 216C totarget block 220A, 220B and 220C respectively present in hierarchies200A, 200B and 200C.

At third level 242, one or more second level transportation collectionsrendered at second level 240 are aggregated by third leveltransportation controller 230, to create third level transportcollection 232. For instance, third level transport collection 232includes second level transport collection 232A from second leveltransportation controller 216A, and similar second level transportcollections 232B, 232C, 232D from their respective second leveltransportation controllers. Third level transportation controller 230transports third level transport collection 232 to second leveltransportation controller 218B and 218C at 234 and 235 respectively.

Further, at second level 240, second level transportation controller218B and 218C transports third level transport collection 232 tohierarchies 200B and 200C at 236 and 237 respectively. Second leveltransportation controller 218B and 218C may also deploy third leveltransport collection 232 at 236 and 237 and transport third leveltransport collection 232 to the corresponding target systems present intarget block 220B and 220C respectively. In an embodiment, third leveltransport collection 232 in association with the second level transportcollection rendered at second level 240 (e.g., 216B and 216C) may betransported to target blocks 220B and 220C. Second level transportationcontroller 218B and 218C may deploy the respective second leveltransport collections to assign the first level transport requestsincluded in them to the respective target systems. At first level 238,the object packets included in the first level transport requests 206A,210A and 214A are assigned to the respective target systems present innested hierarchy of the system landscapes 244. The object packetstransferred to the target block (e.g., 220B and 220C) of hierarchies200B and 200C may have been transported from the source blocks of therespective hierarchies (e.g., 202B and 202C), or from the source systemsof other hierarchies (e.g., 202A).

At first level 238, for hierarchy 200A, the source systems (e.g., 204A,208A, 212A), may be development systems, and the target systems (e.g.,222A, 224A and 226A) may be quality assurance systems and/or productionsystems. The object packets that have to be transferred from thedevelopment systems are identified. The first level transport requestsare generated for a collection of object packets for each developmentsystem. The first level transport requests are aggregated to render asecond level transport collection. The second level transport collectionis transported to the quality assurance systems and/or productionsystems.

However, from a higher level, for instance from second level 240,hierarchy 200A may be a source system or a development system, andhierarchies 200B and 200C may be the target systems or a qualityassurance system and a production system respectively. To transportdevelopment data from development system 200A to quality assurancesystem 200B and production system 200C, transportation controller 218Aof 200A generates transport collection 216A. The transport collection216A is aggregated with one or more of other transport collectionsrendered at one or more hierarchies, to create principle transportcollection 232, at third level 242. Principle transportation controller230 transports principle transport collection 232 to transportationcontrollers 218B and 218C of quality assurance system 200B andproduction system 200C respectively. Transportation controllers 218B and218C transport principle transport collection 232 to quality assurancesystem 200B and production system 200C respectively. Thus the targetblocks of quality assurance system 200B and production system 200C mayhave object packets coming from development system 200A, apart fromtheir own source blocks 202B and 202C respectively.

Thus, in nested hierarchy 244, including three hierarchies of systemlandscapes 200A, 200B and 200C, the transport collection is renderedrecursively to transport object packets from source systems in hierarchyof system landscapes 200A to hierarchy of system landscapes 200B andhierarchy of system landscapes 200C. This method may be applicable tonested system landscapes including multiple hierarchies of systemlandscapes. For instance, the object packets available for transportingfrom the source systems to the target systems at an n^(th) level of thenested hierarchy are identified. An n^(th) level transport request isgenerated for a collection of object packets of each source systempresent in the n^(th) level of the nested hierarchy. The n^(th) leveltransport request is generated in a hierarchy that is identical to thenested hierarchy of the system landscapes. The n^(th) level transportrequests generated for all the source systems at the n^(th) level of thenested hierarchy are aggregated to render an n+1 level transportcollection at an n+1 level of the nested hierarchy. One or more such n+1level transport collections that are rendered at n+1 level of the nestedhierarchy are aggregated to generate an n+2 level transport collectionat an n+2 level of the nested hierarchy. Thus a nested transportcollection is created, including one or more transport collectionsrendered for a nested hierarchy of the system landscapes.

The n+2 level transport collection is transported to within the n+2level of the nested hierarchy. The n+2 level transport collection isdeployed at the n+1 level of the nested hierarchy, to assign the n+1level transport collections present in the n+2 level transportcollection to the corresponding hierarchies present in the nestedhierarchy of system landscapes. Further, the n+1 level transportcollections are deployed at the n^(th) level of the nested hierarchy toassign the n^(th) level transport requests present in each n+1 leveltransport collection to the target systems present in the n^(th) levelof the hierarchy.

By recursively rendering the transport collection, the object packetsfrom source systems are transported to corresponding target systems thatare present in any hierarchy of system landscapes in the nestedhierarchy of the system landscapes. The above method of transportingobject packets may be utilized across multiple levels in the nestedhierarchical arrangement of source and target system.

FIG. 3 illustrates a process diagram for transporting one or more objectpackets present in a nested hierarchy of one or more system landscapes,according to an embodiment of the invention. In process block 305, theobject packets available for transporting from one or more sourcesystems to one or more target systems present in the nested hierarchy ofthe system landscapes are identified. In process block 310, a transportrequest is generated for a collection of object packets of each sourcesystem present in the nested hierarchy of the system landscapes. Thetransport request represents a format of a type of output data includedin the object packets it comprises. Transport requests are generated forall the source systems for the collection of object packets in thesource systems. In process block 315, the transport requests generatedfor all source systems present in the hierarchy of system landscapes areaggregated to render a nested transport collection. The transportcollection represents a format of a type of the object packets includedin the transport request it comprises. In process block 320, the nestedtransport collection rendered for the source systems is transportedwithin the nested hierarchy of the system landscapes. In process block325, the nested transport collection is deployed to assign the transportrequests included in the transport collection to the target systemspresent in the nested hierarchy of the system landscapes.

In an embodiment, the object packets available at the source systems ofa primary level of a hierarchy of system landscapes are identified. Theprimary level of the hierarchy may include a group of source systems anda group of target systems. Primary level transport requests aregenerated for a collection of object packets for each of the sourcesystems. The primary level transport requests are aggregated to render asecondary level transport collection at a secondary level of thehierarchy. The secondary level of the hierarchy may include one or moretransport collections rendered for corresponding hierarchies of thesystem landscapes. All the secondary level transport collections areaggregated at a tertiary level of the hierarchy, to generate a tertiarylevel transport collection. The tertiary level transport collection istransported back to the secondary level. At the tertiary level, thetertiary level transport collection is transported within the nestedhierarchy. At the secondary level, the tertiary level transportcollection is deployed to assign the secondary level transportcollections included in the tertiary level transport collection to therespective hierarchies. The secondary level transport collections arefurther transported to the respective target blocks and deployed at theprimary level, to assign the target requests to the respective targetsystems. The object packets present in the transport requests areextracted by the target systems at the primary level of the nestedhierarchy.

In an embodiment, the system landscape includes a development system, aquality assurance system and a production system. An output of thedevelopment system is transported to the quality assurance system andthe production system. The development system may include a sourcesystem, and the quality assurance system and the production system mayinclude a target system each. The output of the development systemincludes one or more object packets that have to be transported to thequality assurance system and the production system. The object packetsavailable for transporting from one or more such development systems toone or more quality assurance systems and one or more production systemsare identified. The development systems, the quality assurance systemsand the production systems are present in a first hierarchy of thesystem landscapes. A transport request is generated for each collectionof object packets from each development system. The transport requestsare aggregated to render a transport collection. The transportcollection is transported to the quality assurance system and productionsystem, and deployed to assign the transport requests present in thetransport collection to the respective quality assurance systems and theproduction systems.

In an embodiment, the transport request represents a request format thatis identical to an object format of the object packets included in thetransport requests. The transport collection represents a collectionformat that is identical to the request format of the aggregatedtransport requests.

In an embodiment, deploying the transport collection includes importingthe transport collection at the target system (for e.g. qualityassurance system or production system) and extracting the transportrequests present in the transport collection for each target system.Further, the source systems associated with the transport requests areidentified to determine the corresponding target systems. The objectpackets included in the transport requests are identified and assignedto the corresponding target systems.

In an embodiment, an index may be created for generating an identity foreach source system and each target system. The identity may be describedas an address of the system that shows an association it shares withother systems. For instance, the identity may provide an associationbetween a source system and one or more target systems. This identitymay be used to determine the target systems that correspond to thesource systems. The index may create a mapping between the sourcesystems and the corresponding target systems, to facilitate thedetermination of target systems that correspond to the source systems.

FIG. 4 illustrates a block diagram of a system for transporting one ormore object packets present in a nested hierarchy of one or more systemlandscapes, according to an embodiment of the invention. Computer system400 is utilized for analyzing the data within the data report. Someembodiments of the invention may include the above-described methods asbeing written as one or more software components. These components, andthe functionality associated with them, represented as computer system400 may include source block 405, transportation controller 410,development controller 415, request generator 420, request accumulator425, transport controller 430, index 435 and target block 440. In anembodiment, development controller 415 is in communication with requestgenerator 420. Request generator 420 is in communication with requestaccumulator 425 and index 435. Request accumulator 425 is incommunication with transport controller 430. In an embodiment,development controller 415, request generator 420, request accumulator425, transport controller 430 and index 435 are included intransportation controller 410. Transportation controller 410 is incommunication with source block 405 and target block 440. In anotherembodiment, computer system 400 includes a processor operable forreading and executing instructions and a memory element for storing theinstructions operable for transporting object packets from sourcesystems to corresponding target systems.

The source systems and the target systems of a hierarchy of systemlandscapes may be collectively termed as source block 405 and targetblock 440 respectively. The source systems may be responsible forexecuting one or more processes to render a collection of output data.The output data may be required for further processing at target block440. Transportation controller 410 transports the output data fromsource block 405 to target block 440.

For transporting the output data, transportation controller 410 employsdevelopment controller 415, request generator 420, request accumulator425 and transport controller 430. Development controller 415 is operablefor identifying object packets of each source system present in systemblock 405 of each hierarchy of system landscapes that is available fortransporting to target systems present in target block 440 of the nestedhierarchy of the system landscapes. An object packet is a collection ofthe output data that may result from one or more processes executed at acorresponding source system. The object packets may include output dataof various applications that are associated with a corresponding sourcesystem. Request generator 420 is operable for generating a transportrequest for a collection of object packets at each source system insystem block 405 present in the hierarchy of system landscapes. Atransport request represents a collection of object packets that areavailable in a source system for transporting to one or more targetsystem. Request generator 420 generates a transport request for eachsuch collection of object packets in each source system present insource block 405 of the nested hierarchy of the system landscapes. Thus,an output of request generator 420 may include many transport requests,each representing a collection of object packets of one source systempresent in source block 405 of the hierarchy of system landscapes.

Request accumulator 425 is operable for aggregating the transportrequests generated for the source systems, to render a transportcollection. A transport collection represents a collection of transportrequests that are generated for each collection of object packetsavailable in each source system. Transport controller 430 is operablefor transporting the transport collection to corresponding targetsystems present in the nested hierarchy of the system landscapes. In anembodiment, transport controller 430 is operable for transporting thetransport collection to corresponding target systems present in ahierarchy of system landscapes same as the hierarchy of systemlandscapes in which the source systems are present. In anotherembodiment, transport controller 430 is operable for transporting thetransport collection to corresponding target systems present in ahierarchy of system landscapes that is different from the hierarchy ofsystem landscapes in which the source systems are present. In anembodiment, transport controller 430 is responsible for exporting thetransport collection and deploying the transport collection atcorresponding target systems.

Transport controller 430 is operable for deploying the transportcollection at corresponding target systems present in the nestedhierarchy of the system landscapes. Deploying the transport collectionmay include importing the transport collection rendered for the sourcesystems, extracting the transport request present in the transportcollection, identifying the source systems associated with eachtransport request, identifying the object packets available in eachtransport request, and assigning the object packets of each sourcesystem to a corresponding target system.

Index 435 in communication with transport controller 430 may store atransport directory that contains an identity of the source systems andthe corresponding target systems. For instance, the transport directoryincludes an address AAAS of a source system and a corresponding addressAAAT of a corresponding target system. The identity facilitatesidentification of a corresponding target system for every source system.Based upon the transport directory, transport controller 430 transportsthe transport collection to corresponding target systems.

In an embodiment, index 435 is operable to map the source systems andthe corresponding target systems based upon the identity that exists inthe transport directory. Mapping the source systems and thecorresponding target systems includes identifying a corresponding targetsystem for every source system, based upon an identity of the sourcesystem and the target system, and associating the corresponding targetsystem with the source system. In an embodiment, index 435 generates anidentity for each source system based upon the output data included inthe transport requests of the transport collection rendered by requestaccumulator 425. Based upon the generated identity, a correspondingtarget system is identified. Based upon the identified target systems,transport controller 430 transports the transport collection and deploysthe transport collections at the respective target systems.

Some embodiments of the invention may include the above-describedmethods being written as one or more software components. Thesecomponents, and the functionality associated with each, may be used byclient, server, distributed, or peer computer systems. These componentsmay be written in a computer language corresponding to one or moreprogramming languages such as, functional, declarative, procedural,object-oriented, lower level languages and the like. They may be linkedto other components via various application programming interfaces andthen compiled into one complete application for a server or a client.Alternatively, the components maybe implemented in server and clientapplications. Further, these components may be linked together viavarious distributed programming protocols. Some example embodiments ofthe invention may include remote procedure calls being used to implementone or more of these components across a distributed programmingenvironment. For example, a logic level may reside on a first computersystem that is remotely located from a second computer system containingan interface level (e.g., a graphical user interface). These first andsecond computer systems can be configured in a server-client,peer-to-peer, or some other configuration. The clients can vary incomplexity from mobile and handheld devices, to thin clients and on tothick clients or even other servers.

The above-illustrated software components are tangibly stored on acomputer readable medium as instructions. The term“computer readablemedium” should be taken to include a single medium or multiple mediathat stores one or more sets of instructions. The term “computerreadable medium” should be taken to include any physical article that iscapable of undergoing a set of physical changes to physically store,encode, or otherwise carry a set of instructions for execution by acomputer system which causes the computer system to perform any of themethods or process steps described, represented, or illustrated herein.Examples of computer-readable media include, but are not limited to:magnetic media, such as hard disks, floppy disks, and magnetic tape;optical media such as CD-ROMs, DVDs and holographic devices;magneto-optical media; and hardware devices that are speciallyconfigured to store and execute, such as application-specific integratedcircuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAMdevices. Examples of computer readable instructions include computercode, such as produced by a compiler, and files containing higher-levelcode that are executed by a computer using an interpreter. For example,an embodiment of the invention may be implemented using Java, C++, orother object-oriented programming language and development tools.Another embodiment of the invention may be implemented in hard-wiredcircuitry in place of, or in combination with computer readable softwareinstructions.

FIG. 5 illustrates a block diagram of an exemplary computer system andenvironment for implementing the principles and techniques discussedherein for transporting one or more object packets present in a nestedhierarchy of one or more system landscapes, according to an embodimentof the invention. Computing device 500 includes processor 510 thatexecutes software instructions or code stored on computer readablemedium 550 to perform the above-illustrated methods of the invention.Computing device 500 includes media reader 545 to read the instructionsfrom computer readable medium 550 and store the instructions in storage520 or memory or random access memory (RAM) 515. Storage 520 provides alarge space for keeping static data where at least some instructionscould be stored for later execution. The stored instructions may befurther compiled to generate other representations of the instructionsand dynamically stored in memory 515. Processor 510 reads instructionsfrom memory 515 and performs actions as instructed.

According to one embodiment of the invention, computing device 500further includes output device 525 (e.g., a display) to provide at leastsome of the results of the execution as output including, but notlimited to, visual information to users and input device 530 to providea user or another device with means for entering data and/or otherwiseinteract with computing device 500. Each of these output and inputdevices could be joined by one or more additional peripherals to furtherexpand the capabilities of computing device 500. Network communicator535 may be provided to connect computing device 500 to network 505 andin turn to other devices connected to network 505 including otherclients, servers, data stores, and interfaces, for instance. The modulesof computing device 500 are interconnected via system bus 560. Computingdevice 500 includes data source interface 540 to access data source 555.Data source 555 can be accessed via one or more abstraction layersimplemented in hardware or software. For example, data source 555 may beaccessed by network 505. In some embodiments, data source 555 may beaccessed via an abstraction layer, such as, a semantic layer.

A data source is an information resource. Data sources include sourcesof data that enable data storage and retrieval. Data sources may includedatabases, such as, relational, transactional, hierarchical,multi-dimensional (e.g., OLAP), object oriented databases, and the like.Further data sources include tabular data (e.g., spreadsheets, delimitedtext files), data tagged with a markup language (e.g., XML data),transactional data, unstructured data (e.g. text files, screenscrapings), hierarchical data (e.g., data in a file system, XML data),files, a plurality of reports, and any other data source accessiblethrough an established protocol, such as, Open DataBase Connectivity(ODBC), produced by an underlying software system (e.g. ERP system), andthe like. Data sources may also include a data source where the data isnot tangibly stored or otherwise ephemeral such as data streams,broadcast data, and the like. These data sources can include associateddata foundations, semantic layers, management systems, security systemsand so on.

In an embodiment, transporting object packets present in the hierarchyof system landscapes involves transporting object packets from thesource systems of a hierarchy of system landscape to the correspondingtarget systems of the hierarchy of system landscape. In anotherembodiment, transporting object packets present in the hierarchy ofsystem landscapes involves transporting object packets from sourcesystems of a first hierarchy of system landscapes to correspondingtarget systems of a second hierarchy of system landscapes. The first andthe second hierarchy of system landscapes are included in the nestedhierarchy of the system landscapes.

The target systems that receive the object packets are present in thehierarchy of system landscapes whose structure is similar to thehierarchy of system landscapes that include the source systems thattransport the object packets. Storage 520 may store metadata of thesource systems and the corresponding target systems. The metadata storedin storage 520 may includes details about each source system andcorresponding target system, like a type of data that each source systemoutputs, a type of development activity performed for each sourcesystem, identity of a corresponding target system for each sourcesystem, etc. In an embodiment, a group of source systems whose objectpackets are being transported may be selected from input device 530.

To transport the object packets from source systems to correspondingtarget systems, the object packets of each source system present in thenested hierarchy of the system landscapes are identified. For acollection of object packets of each source system present in thehierarchy of system landscapes that has to be transported to one or morecorresponding target system present in the nested hierarchy of thesystem landscapes, a transport request is generated for each sourcesystem. The transport requests of all the source systems present in thehierarchy of system landscapes are aggregated to render a transportcollection. In an embodiment, the transport collection may be renderedon output device 525. The transport collection rendered for thetransport requests of the source systems present in the hierarchy ofsystem landscapes is transported to the target systems present in thenested hierarchy of the system landscapes. In an embodiment, networkcommunicator 535 may be utilized to transport the transport collectionfrom the source systems to the corresponding target systems. Thetransport collections are deployed at the target systems present in thenested system landscapes, to assign the object packets contained in thetransport requests at the respective target systems.

The above descriptions and illustrations of embodiments of theinvention, including what is described in the Abstract, is not intendedto be exhaustive or to limit the invention to the precise formsdisclosed. While specific embodiments of, and examples for, theinvention are described herein for illustrative purposes, variousequivalent modifications are possible within the scope of the invention,as those skilled in the relevant art will recognize. These modificationscan be made to the invention in light of the above detailed description.Rather, the scope of the invention is to be determined by the followingclaims, which are to be interpreted in accordance with establisheddoctrines of claim construction.

What is claimed is:
 1. An article of manufacture, comprising anon-transitory computer-accessible medium comprising computer readableinstructions which when executed by a computer, cause the computer toexecute a method comprising: identifying one or more object packets fortransporting from one or more source systems to one or more targetsystems, the one or more source systems and the one or more targetsystems being present in a nested hierarchy of one or more systemlandscapes associated with one or more system landscape processes;generating a transport request for a collection of one or more objectpackets of each of the one or more source systems present in the nestedhierarchy of the one or more system landscapes; aggregating thetransport requests generated for the source systems of each systemlandscape to render one or more corresponding nested transportcollections in a nested aggregation hierarchy identical to the nestedhierarchy of the system landscapes, the nested transport collectionscorresponding to the system landscape processes; transporting the nestedtransport collections from the source systems to the target systemswithin the nested hierarchy of the system landscapes; and deploying thenested transport collections to assign the transport requests present inthe nested transport collections to the corresponding target systemspresent in the nested hierarchy of the one or more system landscapes. 2.The article of manufacture of claim 1, wherein the nested hierarchy ofone or more system landscapes comprises one or more hierarchies of oneor more system landscapes, each hierarchy including one or more systemlandscapes, each system landscape including one or more source systemsand one or more target systems.
 3. The article of manufacture of claim1, wherein identifying the one or more object packets comprisesidentifying the one or more object packets available at the one or moresource systems of a first level of a hierarchy of one or more systemlandscapes, the first level of the hierarchy of the one or more systemlandscapes including one or more source systems and corresponding one ormore target systems.
 4. The article of manufacture of claim 1, whereinaggregating the one or more transport requests comprises aggregating theone or more transport requests to render a transport collection at asecond level of a hierarchy of one or more system landscapes, the secondlevel of the hierarchy of the one or more system landscapes includingone or more transport collections rendered for corresponding one or morehierarchies of the one or more system landscapes.
 5. The article ofmanufacture of claim 1, wherein the method further comprises:identifying the one or more object packets available for transportingfrom the one or more source systems to the one or more target systems ata first level of the nested hierarchy of the one or more systemlandscapes; generating a first level transport request for a collectionof one or more object packets of each of the one or more source systemspresent in the first level of the nested hierarchy of the one or moresystem landscapes; aggregating one or more first level transportrequests generated for the one or more source systems at the first levelof the nested hierarchy of the one or more system landscapes to render asecond level transport collection at a second level of the nestedhierarchy of the one or more system landscapes; aggregating one or moresecond level transport collections rendered at the second level of thenested hierarchy of the one or more system landscapes, to generate athird level transport collection at a third level of the nestedhierarchy of the one or more system landscapes; transporting the thirdlevel transport collection within the third level of the nestedhierarchy of the one or more system landscapes; deploying the thirdlevel transport collection at the third level of the nested hierarchy ofthe one or more system landscapes, to assign the one or more secondlevel transport collections present in the third level transportcollection to the second level of the nested hierarchy of the one ormore system landscapes; and deploying the one or more second leveltransport collections at the second level of the nested hierarchy of theone or more system landscapes, to assign the one or more first leveltransport requests present in each of the one or more second leveltransport collections to the one or more target systems present in firstlevel of nested hierarchy of the one or more system landscapes.
 6. Thearticle of manufacture of claim 5, wherein the second level of thenested hierarchy of the one or more system landscapes comprises:rendering one or more second level transport collections for one or moresecond level hierarchies present in the second level of the nestedhierarchy of the one or more system landscape; aggregating the thirdlevel transport collection deployed at the one or more second levelhierarchies present in the second level of the nested hierarchy of theone or more system landscapes with the one or more second leveltransport collections to generate an aggregated second level transportcollection; and deploying the aggregated second level transportcollection at the first level of the nested hierarchy of the one or moresystem landscapes.
 7. The article of manufacture of claim 1, whereintransporting the transport collection comprises transporting thetransport collection to one or more target systems corresponding to oneor more source systems at a first level of a nested hierarchy of the oneor more system landscapes.
 8. The article of manufacture of claim 1,wherein transporting the transport collection comprises transporting thetransport collection associated with one or more source systems of afirst hierarchy of one or more system landscapes to one or more targetsystems present in a second hierarchy of one or more system landscapes.9. The article of manufacture of claim 1, wherein transporting the oneor more object packets further comprises transporting the one or moreobject packets from a source system of a first hierarchy of one or moresystem landscapes to a target system of the first hierarchy of the oneor more system landscapes.
 10. The article of manufacture of claim 1,wherein transporting the one or more object packets further comprisestransporting the one or more object packets from a source system of afirst hierarchy of one or more system landscapes to a target system of asecond hierarchy of one or more system landscapes.
 11. The article ofmanufacture of claim 1, wherein a system landscape comprises adevelopment system, a quality assurance system, and a production system.12. The article of manufacture of claim 11, wherein an output of thedevelopment system is transported to the quality assurance system andthe production system, the development system comprising a sourcesystem, and the quality assurance system and the production systemcomprising corresponding one or more target systems, the output of thedevelopment system including one or more object packets of thedevelopment system.
 13. The article of manufacture of claim 12, whereinthe method further comprises: identifying the one or more object packetsavailable for transporting from one or more development systems to oneor more quality assurance systems and one or more production systems,the one or more development systems, the one or more quality assurancesystems and the one or more production systems present in a firsthierarchy of the one or more system landscapes; generating a transportrequest for a collection of one or more object packets of each of theone or more development systems; aggregating one or more transportrequests generated for the one or more development systems to render atransport collection; transporting the transport collection to the oneor more quality assurance systems and one or more production systems;and deploying the transport collection to assign the one or moretransport requests present in the transport collection to the one ormore quality assurance systems and the one or more production systems.14. The article of manufacture of claim 1, wherein the transport requestcomprises a request format identical to an object format of thecorresponding one or more object packets.
 15. The article of manufactureof claim 1, wherein the transport collection comprises a collectionformat identical to a request format of the corresponding one or moreaggregated transport requests.
 16. The article of manufacture of claim1, wherein deploying the transport collection comprises: importing thetransport collection rendered for the one or more source systems to thesecond level of the nested hierarchy of the one or more systemlandscapes; at the first level of the nested hierarchy of the one ormore system landscapes, extracting the one or more transport requestspresent in the transport collection for each of the corresponding one ormore target system; at the first level of the nested hierarchy of theone or more system landscapes, identifying the one or more sourcesystems associated with each of the one or more transport request; atthe first level of the nested hierarchy of the one or more systemlandscapes, identifying the one or more object packets available in thetransport request of each of the one or more source systems; and at thefirst level of the nested hierarchy of the one or more systemlandscapes, assigning the one or more object packets of each of the oneor more source systems to the corresponding target system.
 17. Thearticle of manufacture of claim 1 wherein the method further comprises:creating an index for generating an identity for each of the one or moresource systems and each of the one or more target systems and mappingthe one or more source systems and the one or more target systemsassociated.
 18. A computer implemented method for transporting one ormore object packets present in a nested hierarchy of one or more systemlandscapes, comprising: identifying the object packets for transportingfrom one or more source systems to one or more target systems, the oneor more source systems and the one or more target systems being presentin the nested hierarchy of the one or more system landscapes associatedwith one or more system landscape processes; generating a transportrequest for a collection of one or more object packets of each of theone or more source systems present in the nested hierarchy of the one ormore system landscapes; aggregating the transport requests generated forthe source systems of each system landscape to render one or more nestedtransport collections in a nested aggregation hierarchy identical to thenested hierarchy of the one or more system landscapes, the nestedtransport collections corresponding to the system landscape processes;transporting the one or more nested transport collections from thesource systems to the target systems within the nested hierarchy of thesystem landscapes; and deploying the nested transport collections toassign the transport requests present in the nested transportcollections to the corresponding target systems present in the nestedhierarchy of the one or more system landscapes.
 19. A computing deviceoperable for transporting one or more object packets present in a nestedhierarchy of one or more system landscapes comprising: a processoroperable for reading and executing instructions stored in one or morememory elements; and the one or more memory elements storinginstructions for: a development controller operable for identifying theone or more object packets available for transporting from one or moresource system present in the hierarchy of one or more system landscapesto one or more corresponding target system present in a nested hierarchyof the one or more system landscapes, the nested hierarchy of the one ormore system landscapes including the hierarchy of one or more systemlandscapes; a request generator operable for generating a transportrequest for a collection of one or more object packets of each of theone or more source systems present in the nested hierarchy of the one ormore system landscapes; a request accumulator operable for aggregatingthe one or more transport requests generated for the one or more sourcesystems to render a transport collection; and a transport controlleroperable for transporting the transport collection rendered for the oneor more source systems to the corresponding one or more target systemspresent in the nested hierarchy of the one or more system landscapes anddeploying the transport collection to assign the one or more transportrequests present in the transport collection to the corresponding one ormore target systems.
 20. The computing device of claim 19, furthercomprising an index operable for storing a transport directory, thetransport directory including an identity of the one or more sourcesystems and the corresponding one or more target systems and mapping theone or more source systems and the corresponding one or more targetsystems.